GXHandleAlertFilter
You need to override theGXHandleAlertEvent
message if you are providing custom handling of printing alerts. Your override code of theGXHandleAlertEvent
message must match the following formal declaration:
OSErr MyGXHandleAlertFilter (gxJob aJob, gxStatusRecord *aStatus, DialogPtr aDialog, EventRecord *aEventRecord, short *itemHit, Boolean *returnImmed);
ajob
- The job object that is associated with the dialog box.
aStatus
- A pointer to the status record that describes the alert.
aDialog
- A pointer to information about the dialog box that is displaying the alert information.
aEventRecord
- A pointer to information about the event that is being handled.
itemHit
- A pointer to the ID of the item in the dialog box in which the event occurred.
returnImmed
On return, a Boolean value that istrue
if the filter procedure completely handled the event (no further event processing needs to be done) andfalse
if the filter procedure did not completely handle the event.- function result
- An error code. The value
noErr
indicates that the operation was successful.DESCRIPTION
QuickDraw GX sends theGXHandleAlertFilter
message when a user-initiated event occurs in a printing alert box.The default implementation of this message handles events that occur in the the printing alert box. If you have customized the printing alert box, you need to handle those events as necessary.
In your override, you need to check the event. If the status event dismisses the printing alert box, set the
returnImmed
parameter value totrue
.SPECIAL CONSIDERATIONS
You never send theGXHandleAlertFilter
message yourself.If you handle the event, you must totally override the
GXHandleAlertFilter
message. Otherwise, forward the message so that another message handler can process the event.RESULT CODES
gxSegmentLoadFailedErr A required code segment could not be found,
or there was not enough memory to load it.gxPrUserAbortErr The user has canceled printing.
Main | Page One | What's New | Apple Computer, Inc. | Find It | Contact Us | Help